docs: clarify pip index configuration during PyPI migration - #2119
Open
harshitethic wants to merge 1 commit into
Open
docs: clarify pip index configuration during PyPI migration#2119harshitethic wants to merge 1 commit into
harshitethic wants to merge 1 commit into
Conversation
Member
|
It's unclear if PyPUG should contain individual tools' docs instead of pointing to them. Have you checked previous PR discussions? Said tools evolve independently and get own documentation updates sooner. We should probably give a more generic advice as some of the PRs attempted but didn't get to complete the effort. #2048 seems to have been solid but didn't get early reviews. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #463
Validation
📚 Documentation preview 📚: https://python-packaging-user-guide--2119.org.readthedocs.build/en/2119/